Unmanned aerial vehicle impact monitoring system

ABSTRACT

According to one aspect of the present disclosure, a device and technique for unmanned aerial vehicle (UAV) impact monitoring includes a UAV having a propulsion system configured to fly the UAV to a destination; a retention mechanism for retaining and releasing a package carried by the UAV; and an indicator reader module configured to determine a status of an impact indicator attached to the package.

BACKGROUND

To save time and also potentially money, distributors and sellers of goods have been attempting to deploy unmanned aerial vehicles (UAVs) to handle customer shipments. These UAVs have distinct advantages since they can be automated or remotely controlled. This allows for savings in labor.

UAV airborne delivery also provides for very fast service. Under a conventional package delivery service, a customer orders an item, the item is placed on one truck, and then the item is transported by the truck from a warehouse to a distribution center. The item is then unloaded at one area (incoming) of the distribution center, is moved to a sorting area of the distribution center, and then moved to a loading (shipment) area, where the item is placed on a pallet that is waiting for an outgoing truck. After placing the item on the outgoing truck, the item is then transported on the truck or van from the distribution center to the ultimate delivery destination area.

However, with a UAV, after the customer orders an item, the UAV delivery process results in much faster delivery. The item (in some embodiments in a package) is loaded onto the UAV, the UAV is launched, the UAV reaches the delivery destination area, and the UAV then delivers the package.

There are multiple ways in which a UAV may deliver a package at the desired destination. For example, the UAV could land, release the package, and then take off. The UAV may also hover above the delivery destination, lower the package from the UAV to the ground using a line or tether, release the package, and then retract the tether. The UAV may also release the package from a relatively small distance above a landing area (e.g., with or without a parachute to slow the descent of the package to the landing area).

BRIEF SUMMARY

According to one aspect of the present disclosure, a device and technique for unmanned aerial vehicle (UAV) impact monitoring is disclosed. The system and technique includes unmanned aerial vehicle (UAV) having a propulsion system configured to fly the UAV to a destination; a retention mechanism for retaining and releasing a package carried by the UAV; and an indicator reader module configured to determine a status of an impact indicator attached to the package.

According to another embodiment of the present disclosure, a system and technique includes a UAV having a propulsion system configured to fly the UAV to a destination; a retention mechanism for retaining and releasing a package carried by the UAV; and an indicator reader module. The indicator reader module is configured to, prior to the retention mechanism releasing the package at the destination, determine a status of an impact indicator attached to the package and, responsive to determining that the status indicates an activation of the impact indicator, abort a release of the package by the retention mechanism at the destination.

According to yet another embodiment of the present disclosure, a system and technique includes a UAV having a propulsion system configured to fly the UAV to a destination; a retention mechanism for retaining and releasing a package carried by the UAV; and an indicator reader module. The indicator reader module is configured to, prior to picking up the package by the retention mechanism, determine a status of an impact indicator attached to the package and, responsive to determining that the status indicates a non-activation of the impact indicator, pick up the package by the retention mechanism.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

For a more complete understanding of the present application, the objects and advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

FIGS. 1A and 1B are diagrams illustrating respective front and rear views of an embodiment of an impact indicator according to the present disclosure;

FIGS. 2A and 2B are diagrams illustrating respective front and rear views of the impact indicator of FIGS. 1A and 1B in an activated state according to the present disclosure;

FIG. 3A is a diagram illustrating an enlarged view of a portion of the impact indicator illustrated in FIG. 2B in accordance with the present disclosure;

FIG. 3B is a diagram illustrating an enlarged view of a portion of the impact indicator illustrated in FIG. 3A in accordance with the present disclosure;

FIG. 4A is another diagram illustrating an enlarged view of a portion of the impact indicator of FIGS. 1A and 1B in an activated state according to the present disclosure;

FIG. 4B is a diagram illustrating an enlarged view of a portion of the impact indicator illustrated in FIG. 4A in accordance with the present disclosure;

FIG. 5A is a diagram illustrating another embodiment of an impact indicator according to the present disclosure;

FIG. 5B is a diagram illustrating an enlarged view of a portion of the impact indicator illustrated in FIG. 5A in accordance with the present disclosure;

FIG. 6 is a diagram illustrating an enlarged view of a portion of the impact indicator illustrated in FIGS. 5A and 5B in an activated state in accordance with the present disclosure;

FIG. 7A is a diagram illustrating an enlarged view of a portion of the impact indicator illustrated in FIGS. 5A and 5B in another activated state in accordance with the present disclosure;

FIG. 7B is a diagram illustrating an enlarged view of a portion of the impact indicator illustrated in FIG. 7A in accordance with the present disclosure;

FIG. 8 is a block diagram illustrating an embodiment of an impact indicator according to the present disclosure;

FIG. 9 is a diagram illustrating a perspective rear view of a portion of an embodiment of the impact indicator of FIG. 8 according with the present disclosure;

FIG. 10 is a diagram illustrating a section view of an embodiment of the impact indicator of FIG. 9 according to the present disclosure taken along the line 10-10 in FIG. 9;

FIG. 11 is a diagram illustrating an enlarged view of a portion of the impact indicator depicted in FIG. 10 according to an embodiment of the present disclosure;

FIG. 12 is a diagram illustrating another embodiment of an impact indicator in accordance with the present disclosure;

FIG. 13 is a diagram illustrating a bottom view of the impact indicator of FIG. 12 in accordance with an embodiment of the present disclosure viewed from the line 13-13 in FIG. 12;

FIG. 14 is a diagram illustrating a side view of the impact indicator depicted in FIG. 12 in accordance with an embodiment of the present disclosure viewed from the line 14-14 of FIG. 12;

FIGS. 15A and 15B are diagrams illustrating a portion of the impact indicator depicted in FIGS. 12-14 according to an embodiment of the present disclosure;

FIG. 16 is a diagram illustrating another embodiment of an impact indicator in accordance with the present disclosure;

FIG. 17 is a diagram illustrating a bottom view of the impact indicator of FIG. 16 in accordance with an embodiment of the present disclosure viewed from the line 17-17 in FIG. 16;

FIG. 18 is a diagram illustrating a section view of the impact indicator depicted in FIG. 16 in accordance with an embodiment of the present disclosure taken along the line 18-18 of FIG. 16;

FIG. 19 is a diagram illustrating another embodiment of an impact indicator in accordance with the present disclosure;

FIG. 20 is a diagram illustrating another embodiment of an impact indicator in accordance with the present disclosure;

FIG. 21 is a diagram illustrating a portion of the impact indicator depicted in FIG. 20 according to an embodiment of the present disclosure;

FIG. 22 is a block diagram illustrating an embodiment of an unmanned aerial vehicle (UAV) impact monitoring system according to the present disclosure;

FIG. 23 is a diagram illustrating an embodiment of a UAV impact monitoring system according to the present disclosure; and

FIG. 24 is a flow diagram illustrating an embodiment of a UAV impact monitoring method according to the present disclosure.

DETAILED DESCRIPTION

Embodiments of the present disclosure provide a device, system, method and technique for unmanned aerial vehicle (UAV) impact monitoring. According to one embodiment, the system and technique includes a UAV having a propulsion system configured to fly the UAV to a destination; a retention mechanism for retaining and releasing a package carried by the UAV; and an indicator reader module configured to determine a status of an impact indicator attached to the package. Embodiments of the present disclosure enable impact and/or acceleration event detection of a package being transported/delivered by the UAV. The UAV is configured to acquire one or more types of data pertaining to an impact indicator affixed to and/or otherwise associated with the package to determine if the package has been subject to an impact event that may otherwise cause damage to the package. If an activated status is determined for the impact indicator (indicating that the package has been subjected to an impact event of sufficient magnitude to cause the impact indicator to display and/or otherwise indicate a positive impact status, the UAV may abort the delivery, re-acquire the package for the return thereof to its destination, etc.

With reference now to the Figures and in particular with reference to FIGS. 1A and 1B, exemplary diagrams of an impact indicator 10 are provided in which illustrative embodiments of the present disclosure may be implemented. FIG. 1A is a diagram illustrating a front view of impact indicator 10, and FIG. 1B is a diagram illustrating a rear view of impact indicator 10. In FIGS. 1A and 1B, indicator 10 is a portable device configured to be affixed to or disposed within a transport container containing an object of which impact and/or acceleration events associated therewith are to be monitored. Embodiments of impact indicator 10 monitor whether an object has been exposed to an impact or some level of an acceleration event during manufacturing, storage and/or transport of the object. In some embodiments, impact indicator 10 may be affixed to a transport container using, for example, adhesive materials, permanent or temporary fasteners, or a variety of different types of attachment devices. The transport container may include a container in which a monitored object is loosely placed or may comprise a container of the monitored object itself. It should be appreciated that FIGS. 1A and 1B are only exemplary and are not intended to assert or imply any limitation with regard to the environments in which different embodiments may be implemented.

In the embodiment illustrated in FIGS. 1A and 1B, impact indicator 10 comprises a housing 12 having a detection assembly 14 disposed therein. In the illustrated embodiment, detection assembly 14 is configured to detect and indicate impact or acceleration events in either of two different directions, indicated by direction 16 or direction 18 relative to indicator 10 in FIG. 1B (i.e., in direction 16/18 or at an angle thereto having a directional vector component in a corresponding direction 16/18). However, it should be understood that assembly 14 may be configured for detecting/indicating an impact event corresponding to a single direction (as will be described further below). Further, it should be understood that additional detection assemblies 14 may be included in indicator 10 to provide impact detection/indication in additional directions.

In some embodiments, housing 12 is configured and/or constructed from a clear or semi-opaque material having a masking label 20 located on a front side thereof or affixed thereto (FIG. 1A). In some embodiments, masking label 20 is configured having one or more apertures or “windows” 22 for providing a visual indication of impact detection. For example, as will be described further below, in response to indicator 10 being subjected to or receiving some predetermined level of impact or acceleration event, detection assembly 14 causes a visual indication to be displayed within or through one or more of windows 22 to provide a visual indication that the monitored object has or may have been subjected to some level of impact. However, it should be understood that other methods may be used to provide a visual indication that detection assembly 14 has moved and/or been otherwise placed into an activated state indicating that indicator 10 has experienced a shock, impact or acceleration event. It should also be understood that housing 12 may be configured and/or manufactured from other materials (e.g., opaque materials having one or more windows 22 formed therein). In some embodiments, housing 12 may be configured without window 22. For example, as will be described in greater detail below, indicator 10 may be configured to provide visual and/or non-visual indications of whether an impact or acceleration condition has been experienced by indicator 10 (e.g., via the use of RFID signals).

Referring to FIG. 1B, detection assembly 14 is illustrated in a non-activated or initial pre-detection state (i.e., prior to being subjected to an acceleration event). In the illustrated embodiment, detection assembly 14 comprises a weight or mass member 30 and spring members 40 and 42. Housing 12 comprises sidewalls 46 and 48 located on opposite sides of mass member 30. Sidewalls 46 and 48 form a translation path to enable movement of mass member 30 within housing 12 in response to housing 12 or indicator 10 being subjected to an acceleration event. For example, in FIG. 1B, mass member 30 is located in a non-activated position 50 within housing 12. Additionally, referring to FIG. 1A, a medial surface portion 52 of mass member 30 is located within and/or is otherwise visible within window 22.

In the embodiment illustrated in FIG. 1B, spring members 40 and 42 bias mass member 30 to the non-activated position 50 in the pre-detection state of indicator 10. For example, in the illustrated embodiment, spring members 40 and 42 comprise leaf springs 56 and 58, respectively; however, it should be understood that other types of biasing elements may be used. In FIG. 1B, sidewall 46 has formed therein recesses or seats 62 and 64 for holding respective ends 68 and 70 of leaf springs 56 and 58. Sidewall 48 has formed therein recesses or seats 74 and 76 for holding respective ends 80 and 82 of leaf springs 56 and 58. Leaf springs 56 and 58 are formed having a length greater than a width of mass member 30 (e.g., as measured in a direction from sidewall 46 to sidewall 48). The ends 68 and 80 of leaf spring 56 are located in respective seats 62 and 74 such that leaf spring 56 is positioned in an orientation transverse to the movement path of mass member 30. The ends 70 and 82 of leaf spring 58 are located in respective seats 64 and 76 such that leaf spring 58 is positioned in an orientation transverse to the movement path of mass member 30. For example, the translation path formed by sidewalls 46 and 48 enables movement of mass member 30 in the directions indicated by 16 and 18.

Ends 68 and 80 of leaf spring 56 are located in seats 62 and 80, and ends 70 and 82 of leaf spring 58 are located in respective seats 64 and 76, such that leaf springs 56 and 58 have convex surfaces facing each other. Thus, in the illustrated embodiment, leaf springs 56 and 58 are biased towards each other. In the embodiment illustrated in FIG. 1B, leaf springs 56 and 58 each extend laterally across a medial portion of mass member 30 between opposing arcuately formed walls 88 and 90 of mass member 30. Leaf springs 56 and 58 are biased toward each other and support mass 30 in the non-activated position 50 (e.g., leaf springs 56 and 58 contact and support respective walls 88 and 90 of mass member 30 to retain mass member 30 in the non-activated position 50). It should be understood that mass member 30 may be otherwise formed and/or spring members 40 and 42 may be otherwise configured and/or positioned relative to mass member 30 to retain and/or bias mass member 30 to the non-activated position 50.

FIGS. 2A and 2B are diagrams illustrating respective front and rear views of indicator 10 illustrated in FIGS. 1A and 1B in an activated state. In the embodiment illustrated in FIGS. 2A and 2B, indicator 10 and/or housing 12 has been subjected to an impact and/or acceleration event in a direction corresponding to direction 16 of a level and/or magnitude to overcome the bias force of spring members 40 and 42 and thereby cause mass member 30 to move from non-activated position 50 to an activated position 96. In response to the acceleration event, leaf spring 56 inverts and a convex portion thereof applies a biasing force against wall 88 of mass member 30 to bias mass member 30 to the activated position 96. Additionally, in response to the acceleration event and movement of mass member 30 to the activated position 96, ends 70 and 82 of leaf spring 58 are drawn out of respective seats 64 and 76. As best illustrated in FIG. 2A, in the activated position 96, a different portion of mass member 30 is located within and/or is otherwise visible in window 22 than when mass member 30 is in the non-activated position 50. For example, in the non-activated position 50, a medial portion of mass member 30 (e.g., medial surface portion 52 (FIG. 1A)) is located within and/or is otherwise visible in window 22. However, in response to movement of mass member 30 to the activated position 96, a surface portion 98 located adjacent medial surface portion 52 is located within and/or is otherwise visible in window 22. As will be described further below, mass member 30 may contain, at different locations thereon, different types and/or forms of indicia on a side thereof facing window 22 corresponding to the non-activated and activated positions of mass member 30 within housing 12 to provide an indication as to whether indicator 10 has been subjected to a certain level or magnitude of acceleration event/impact.

FIG. 3A is a diagram illustrating an enlarged view of a portion of FIG. 2B of indicator 10, and FIG. 3B is a diagram illustrating an enlarged view of a portion of FIG. 3A of indicator 10. Referring to FIGS. 2B, 3A and 3B, as described above, in response to an acceleration event in direction 16 of a level and/or magnitude to overcome the bias force of spring members 40 and 42, leaf spring 56 inverts and a convex portion thereof applies a biasing force against wall 88 of mass member 30 to bias mass member 30 to the activated position 96. Additionally, ends 70 and 82 of leaf spring 58 are drawn out of respective seats 64 and 76. As best illustrated in FIGS. 3A and 3B, sidewalls 46 and 48 have formed therein indent regions 102 and 104, respectively, that are set back and/or offset from adjacent wall surfaces 106, 108, 110 and 112 of sidewalls 46 and 48, respectively. Indent region 102 is located along sidewall 46 between seats 62 and 64, and indent regions 104 is located along sidewall 48 between seats 74 and 76. In response to movement of mass member 30 to the activated position 96, ends 70 and 82 of leaf spring 58 are drawn out of respective seats 64 and 76 and become positioned within respective indent regions 102 and 104. Indent regions 102 and 104 prevent or substantially prevent ends 70 and 82 of leaf spring 58 from returning to respective seats 64 and 76. Thus, if indicator 10 is subjected to another acceleration event in a direction opposite direction 16 (e.g., direction 18) in an attempt to reset and/or re-position mass member 30 in the non-activated position 50 after being in an activated state, indent regions 102 and 104 resist the return of ends 70 and 82 of leaf spring 58 to seats 64 and 76, thereby resulting in an additional bias force in the direction 16 that would need to be overcome in an opposite direction to effectuate movement of mass member 30 toward the non-activated position 50.

FIG. 4A is a diagram illustrating an enlarged view of a portion of indicator 10 with mass member 30 located in another activated position 116 (e.g., on a side of housing 12 opposite activated position 96), and FIG. 4B is a diagram illustrating an enlarged view of a portion of FIG. 4A. For clarity, referring to FIG. 1B, mass member 30 is depicted therein in non-activated position 50. Activated positions 96 and 116 are referenced in FIG. 1B to illustrate locations within housing 12 where mass member 30 will be located when in activated positions 96 and 116. Referring to FIGS. 4A and 4B, if indicator 10 has been subjected to an acceleration event in direction 16 that caused mass member 30 to move to activated position 96 (FIG. 2B) and thereafter is subjected to another acceleration event in direction 18 (e.g., an unauthorized attempt to reseat mass member 30 in the non-activated position 50 or in response to some other impact event) of a level and/or magnitude to overcome the force(s) applied by leaf springs 56 and 58, leaf springs 56 and 58 both collapse or invert and mass member 30 moves from activated position 96, past non-activated position 50, to the activated position 116. For example, in response to the acceleration event in direction 18 of a level and/or magnitude to overcome the force(s) applied by leaf springs 56 and 58, leaf springs 56 and 58 both collapse or invert such that convex portions thereof apply a biasing force against wall 90 of mass member 30 to bias mass member 30 to activated position 116. Additionally, ends 68 and 80 of leaf spring 56 are drawn out of respective seats 62 and 74 and become positioned within respective indent regions 102 and 104. Thus, in response to movement of mass member 30 from activated position 96 to activated position 116, leaf springs 56 and 58 are biased in a same direction (e.g., toward wall 90 of mass member 30) and ends 68, 70, 80 and 82 of respective leaf springs 56 and 58 are located within indent regions 102 and 104, respectively, to prevent or substantially prevent leaf springs 56 and 58 to returning to seat 62, 64, 74 or 76, thereby further preventing or substantially preventing mass member 30 from returning (in a maintained durational state) to non-activated position 50 after being in an activated state.

FIG. 5A is a diagram illustrating another embodiment of indicator 10 in accordance with the present disclosure, and FIG. 5B is a diagram illustrating an enlarged view of a portion of FIG. 5A of indicator 10. In the embodiment illustrated in FIGS. 5A and 5B, sidewalls 46 and 48 each have formed therein an additional spring seat 120 and 122, respectively. Seat 120 is located along sidewall 46 between seats 62 and 64, and seat 122 is located along sidewall 48 between seats 74 and 76. Similar to seats 62, 64, 74 and 76, seats 120 and 122 comprise a recessed area along respective sidewalls 46 and 48 for receiving ends 68/80 and 70/82 of respective leaf springs 56 and 58 in response to indicator 10 being subjected to an impact or acceleration event of sufficient magnitude to cause movement of mass member 30 (e.g., as described above in connection with FIGS. 2A, 3A, 3B, 4A and 4B). For example, FIG. 6 is a diagram illustrating indicator 10 shown in FIGS. 5A and 5B with mass member 30 located in the activated position 96. Because leaf springs 56 and 58 are configured having a length greater than a lateral width of the translation path for movement of mass member 30, the ends of leaf springs 56 and 58 will seek the widest lateral dimension between sidewalls 46 and 48 to relieve tension forces therein. Thus, for example, in response to indicator 10 being subjected to an acceleration event in direction 16 of a magnitude sufficient to overcome the bias forces of leaf springs 56 and 58, mas member 30 will move from non-activated position 50 toward activated position 96, leaf spring 56 will collapse and/or invert and apply a biasing force toward wall 88 of mass member 30, and ends 70 and 82 of leaf spring 58 will be drawn out of respective seats 64 and 76 and become located in respective seats 120 and 122. Seats 120 and 122 102 and 104 prevent or substantially prevent ends 70 and 82 of leaf spring 58 from returning to respective seats 64 and 76. Thus, if indicator 10 is subjected to another acceleration event in a direction opposite direction 16 (e.g., direction 18) in an attempt to reset and/or re-position mass member 30 in the non-activated position 50 after being in an activated state, indent regions 102 and 104 resist the return of ends 70 and 82 of leaf spring 58 to seats 64 and 76, thereby resulting in an additional bias force in the direction 16 that would need to be overcome in an opposite direction to effectuate movement of mass member 30 toward the non-activated position 50.

FIG. 7A is a diagram illustrating an enlarged view of a portion of indicator 10 of FIGS. 5A, 5B and 6 with mass member 30 located in activated position 116, and FIG. 7B is a diagram illustrating an enlarged view of a portion of FIG. 7A. If indicator 10 has been subjected to an acceleration event in direction 16 that caused mass member 30 to move to activated position 96 (FIG. 6) and thereafter is subjected to another acceleration event in direction 18 (e.g., an unauthorized attempt to reseat mass member 30 in the non-activated position 50 or in response to some other impact event) of a level and/or magnitude to overcome the force(s) applied by leaf springs 56 and 58, leaf springs 56 and 58 both collapse or invert and mass member 30 moves from activated position 96, past non-activated position 50, to the activated position 116. For example, in response to the acceleration event in direction 18 of a level and/or magnitude to overcome the force(s) applied by leaf springs 56 and 58, leaf springs 56 and 58 both collapse or invert such that convex portions thereof apply a biasing force against wall 90 of mass member 30 to bias mass member 30 to activated position 116. Additionally, ends 68 and 80 of leaf spring 56 are drawn out of respective seats 62 and 74 and become positioned within respective seats 120 and 122. Thus, in response to movement of mass member 30 from activated position 96 to activated position 116, leaf springs 56 and 58 are biased in a same direction (e.g., toward wall 90 of mass member 30) and ends 68, 70, 80 and 82 of respective leaf springs 56 and 58 are located within seats 120 and 122, respectively, to prevent or substantially prevent leaf springs 56 and 58 to returning to seat 62, 64, 74 or 76, thereby further preventing or substantially preventing mass member 30 from returning (in a maintained durational state) to non-activated position 50 after being in an activated state.

FIG. 8 is a block diagram representing and illustrating an embodiment of indicator 10 in accordance with an embodiment of the present disclosure. In some embodiments, impact indicator 10 may be affixed (permanently or removably) to a printed circuit board and/or otherwise permanently or removably connected to electronic circuitry (e.g., such as a removable cartridge) such that, in response to receipt and/or detection of an acceleration event or impact condition of a sufficient magnitude, impact indicator 10 provides an electronic switch closure or opener that may thereby provide an electronic signal/indication of such event. In FIG. 8, indicator 10 includes a mechanical switching mechanism 80, switch circuitry 82, and a wireless communications module 83 coupled to switch circuitry 82. Mechanical switching mechanism 80 may be any mechanical device used to cause a state change in switch circuitry 82. For example, in some embodiments, mechanism 80 may comprise mass member 30. In such an embodiment (as will be described in greater detail below), movement of mass member 30 may cause a state change in switch circuitry 82 (e.g., changing from an open circuit condition to a closed circuit condition, or vice versa). Switch circuitry 82 may comprise one or more switch elements, contacts, and or circuits that are responsive to movement of mass member 30 (or other type of mechanical switching mechanism 80). Wireless communications module 83 is configured to wirelessly communicate information associated with a state of switch circuitry 82 indicating the activation state of indicator 10 (e.g., based on an open or closed circuit state of circuitry 82). For example, in one embodiment, wireless communications module 83 includes an RFID module 84. In some embodiments, RFID module 84 comprises a passive RFID module 84 (e.g., a passive RFID tag) having an RFID integrated circuit or circuitry 86 (e.g., disposed on or as part of a printed circuit board) and a memory 88, along with an antenna 90. As a passive RFID module 84, indicator 10 does not contain a battery (e.g., power is supplied by an RFID reader 100). For example, when radio waves from reader 100 are encountered by module 84, antenna 90 forms a magnetic field, thereby providing power to module 84 to energize circuit 86. Once energized/activated, module 84 may output/transmit information encoded in memory 88. However, it should be understood that, in some embodiments, RFID module 84 may comprise an active RFID module 84 including a power source (e.g., a battery) that may be configured to continuously, intermittently, and/or according to programmed or event triggers, broadcast or transmit certain information. It should also be understood that wireless communications module 83 may be configured for other types of wireless communication types, modes, protocols, and/or formats (e.g., short-message services (SMS), wireless data using General Packet Radio Service (GPRS)/3G/4G or through public internet via Wi-Fi, or locally with other radio-communication protocol standards such as Wi-Fi, Z-Wave, ZigBee, Bluetooth®, Bluetooth® low energy (BLE), LoRA, NB-IoT, SigFox, Digital Enhanced Cordless Telecommunications (DECT), or other prevalent technologies). As will be described further below, impact indicator 10 functions as a shock fuse such that, in response to receipt of a particular level and/or magnitude of a shock/acceleration event, an electrically conductive member either opens or closes an electronic switch. This configuration enables impact indicator 10 to be used as a passive impact sensor/indicator that can be used as part of an electronic signal or circuit. In some embodiments, the impact sensing capabilities/functions of impact indicator 10 of the present disclosure needs no power while in the monitoring state. When activated, impact indicator 10 completes or opens an electrical path of a circuit and thus could be integrated into most any electronic monitoring system.

In the illustrated embodiment, memory 88 includes at least two different stored and/or encoded values 92 and 94. For example, value 92 may correspond to a value outputted/transmitted by module 84 when switch circuitry 82 is in an open circuit condition or state, and value 94 may correspond to a value outputted/transmitted by module 84 when switch circuitry 82 is in a closed circuit condition or state. As an example, the value 94 may represent an RFID tag identification (ID) number not having an activated impact switch circuitry 82, and the RFID tag's ID number may have an additional character (e.g., “0”) placed at the end thereof. Value 92 may represent the RFID ID number having an activated impact switch circuitry 82, and the RFID tag's ID number may have an additional character at the end thereof being different from the additional character carried by value 94 (e.g., “1”). In the illustrated embodiment, RFID module 84 (e.g., circuitry 86) is coupled to switch circuitry 82 and can detect whether switch circuitry 82 is in an open or closed circuit condition or state. Thus, for example, switch circuitry 82 may initially be in closed circuit condition or state. Thus, if energized/activated, module 84 would transmit value 94 to reader 100. If indicator were to be subject to an impact event, mechanism 80 may cause a change in circuitry 82 that would result in circuitry 82 being in an open circuit condition or state. Thus, if now energized/activated (e.g., after the impact event), module 84 would instead transmit value 92 to reader 100. Thus, embodiments of the present invention enable indicator 10 to monitor sensitive products/objects to which it is attached for potential damage caused by shock using electronic indicators (e.g., RFID readers) while indicator 10 does not contain or require any internal power source (e.g., a battery).

The present invention may include computer program instructions at any possible technical detail level of integration (e.g., stored in a computer readable storage medium (or media) (e.g., memory 88) for causing a processor to carry out aspects of the present invention. Computer readable program instructions described herein can be downloaded to respective computing/processing devices (e.g., communications module 83 and/or RFID module 84). Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages. In some embodiments, electronic circuitry (e.g., circuitry 86) including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention. Aspects of the present invention are described herein with reference to illustrations and/or block diagrams of methods and/or apparatus according to embodiments of the invention. It will be understood that each block of the illustrations and/or block diagrams, and combinations of blocks in the illustrations and/or block diagrams, may represent a module, segment, or portion of code, can be implemented by computer readable program instructions. These computer readable program instructions may be provided to a processor or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the illustrations and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computing device, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the illustrations and/or block diagram block or blocks. Switch circuitry 82, wireless communications module 83, and/or RFID module 84 may be implemented in any suitable manner using known techniques that may be hardware-based, software-based, or some combination of both. For example, switch circuitry 82, wireless communications module 83, and/or RFID module 84 may comprise software, logic and/or executable code for performing various functions as described herein (e.g., residing as software and/or an algorithm running on a processor unit, hardware logic residing in a processor or other type of logic chip, centralized in a single integrated circuit or distributed among different chips in a data processing system). As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, method or computer program product. Accordingly, aspects of the present disclosure may take the form of a hardware embodiment, a software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.”

FIG. 9 is a diagram illustrating a perspective rear view of a portion of an embodiment of indicator 10 in accordance with the present disclosure, FIG. 10 is a diagram illustrating a section view of indicator 10 of FIG. 9 in accordance with an embodiment of the present invention taken along the line 10-10 in FIG. 9, and FIG. 11 is a diagram illustrating an enlarged view of a portion of indicator 10 depicted in FIG. 10. In the embodiment illustrated in FIGS. 9-11, mechanical switching mechanism 80 is formed by mass member 30 having affixed or secured thereto an electrically conductive element 120. In some embodiments, mass member 30 may be formed of a non-metallic or non-conductive material such that conductive element 120 may be secured thereto (e.g., affixed by bonding, fasteners, etc.). In the illustrated embodiment, conductive element 120 extends transversely across mass member 30 in a direction generally orthogonal to the direction of movement of mass member 30 within housing 12 (e.g., movement directions 16 and 18 depicted in FIG. 1B). Conductive member 120 is configured to connect with and/or engage spaced apart contacts 122 and 124 of switch circuitry 82 to cause circuitry 82 to be in either an open circuit condition or state (e.g., when conductive element 120 is disengaged from contacts 122 and 124) or a closed circuit condition or state (e.g., when conductive element 120 is in engagement with contacts 122 and 124). In the illustrated embodiment, conductive element 120 extends linearly across mass member 30 in the direction described above; however, it should be understood that the direction, size, shape, etc., of element 120 may vary (e.g., based on the position and/or locations of contacts 122 and 124). Contacts 122 and 124 comprise electrically conductive pads or segments of circuitry 82. For example, circuitry 82 may comprise one or more electrically conductive wires, traces, pads, posts, and/or electronic components that are coupled to RFID module 84. In FIG. 9, RFID module 84 is omitted from view to better illustrate mass member 30 with conductive element 120; however, it should be understood that contacts 122 and 124 may be coupled to and/or otherwise form part of RFID module 84.

Thus, in operation, in the embodiment illustrated in FIGS. 9-11, circuitry 82 is initially in a closed circuit state when mass member 30 is in the non-activated or initial pre-detection state/position 50 (FIG. 1B (i.e., prior to being subjected to an acceleration event)). Thus, if RFID module 84 is activated or energized by RFID reader 100 while mass member 30 is in the non-activated or initial pre-detection state 50 (i.e., prior to being subjected to an acceleration event), RFID module 84 would detect the closed circuit condition of circuitry 82 and output or transmit value 94. Responsive to indicator 10 being subjected to an impact or acceleration event of a magnitude sufficient to cause movement of mass member 30 from the initial non-activated position 50 to an activated position (e.g., position 96 or 116 (FIGS. 2B and 7A)), the state of circuitry 82 would change from being in a closed circuit condition to being in an open circuit condition because conductive element 120 would have moved away and become disengaged from contacts 122 and 124. Thus, responsive to movement of mass member 30 from the initial non-activated position 50 to an activated position 96 or 116, if RFID module 84 is activated or energized by RFID reader 100, RFID module 84 would detect the open circuit condition of circuitry 82 and output or transmit value 92 instead of value 94. Thus, a change in the switch circuitry 82 state causes a change in a value output by RFID module 84 when activated.

Additionally, embodiments of impact indicator 10 provide a non-reversible indication of impact activation. For example, as described above in connection with FIG. 4A, once mass member 30 leaves the non-activated or pre-activated position 50 in response to an impact event, mass member 30 would remain in either position 96 or 116 (e.g., due to leaf springs 56 and 58), thereby resulting in circuitry 82 remaining in an open state condition and RFID module 84 transmitting value 92 when energized.

In the above description and illustrated embodiment of FIG. 9-11, circuitry 82 is in a closed circuit condition when mass member 30 is in the non-activated or pre-activated position 50. However, it should be understood that indicator 10 may be alternately configured such that circuitry 82 is instead in an open circuit condition when mass member 30 is in the non-activated or pre-activated position 50, and circuitry 82 is in a closed circuit condition when mass member is in position 96 or 116 (e.g., by placing a pair of contacts 122 and 124 near each of positions 96 and 116 (instead of near position 50) which would engage conductive element 120 when mass member 30 is in respective positions 96 or 116). Alternatively, mass member 30 could have multiple spaced apart conductive elements 120 (e.g., one near an upper portion of mass member 30 and one near a lower portion of mass member 30) such that movement of mass member 30 into position 96 or 116 would cause a respective conductive element 120 to come into engagement with contacts 122 and 124 located near position 50 (e.g., the lower conductive element 120 engaging contacts 122 and 124 located near position 50 when mass member is in position 96, and vice versa for when mass member 30 is in position 116). Thus, it should be understood that the placement of conductive element 120 and/or contacts 122 and 124 may vary while enabling RFID module 84 to transmit different values based on whether circuitry 82 is in an open or closed circuit state (based on whether indicator has been subjected to an impact event).

FIG. 12 is a diagram illustrating another embodiment of indicator 10 in accordance with the present disclosure, FIG. 13 is a diagram illustrating a bottom view of indicator 10 of FIG. 12 in accordance with an embodiment of the present invention taken along the line 13-13 in FIG. 12, and FIG. 14 is a diagram illustrating a side view of indicator 10 depicted in FIG. 12 taken along the line 14-14 of FIG. 12. In FIGS. 12-14, most elements of indicator 10 (e.g., those depicted and described in connection with FIGS. 1-7) have been omitted for clarity and ease of description; however, it should be understood that indicator 10 may be similarly configured as depicted and described in connection with FIGS. 1-7. In the embodiment illustrated in FIGS. 12-14, another embodiment of switching mechanism 80, circuitry 82, and RFID module 84 coupled to switch circuitry 82 are depicted. In the illustrated embodiment, switching mechanism 80 is formed by mass member 30 (e.g., without conductive element 120 (FIGS. 9-11)). For ease of description and clarity, mass member 30 is not depicted in FIGS. 13 and 14. Switch circuitry 82 includes conductive switch elements 130 and 132, and conductive contacts 140, 142, 144, and 146. Switch elements 130 and 132 are located generally in or near respective positions 96 and 116 such that as mass member 30 moves into position 96 or 116 from position 50, mass member 30 contacts or otherwise engages respective switch element 130 or 132. In the illustrated embodiment, switch element 130 is fixedly coupled to contact 140, and switch element 132 is fixedly coupled to contact 146. Switch elements 130 and 132, and contacts 140, 142, 144, and 146, may comprise conductive wires, pins, posts, pads, traces, etc.

In the embodiment illustrated in FIGS. 12-14, switch element 130 includes contiguous switch element segments 150, 152, and 154 where segment 150 is fixedly coupled to contact 140. Switch element 130 comprises a flexible switch element 130 such that segments 150, 152, and 154 are movable in angular relationship relative to each other, and segment 150 may bend/rotate relative to and/or with contact 140. Similarly, switch element 132 includes contiguous switch element segments 156, 158, and 160 where segment 156 is fixedly coupled to contact 146. Switch element 132 also comprises a flexible switch element 132 such that segments 156, 158, and 160 are movable in angular relationship relative to each other, and segment 156 may bend/rotate relative to and/or with contact 146. In the illustrated embodiment, switch elements 130 and 132 include non-linear switch element segments 150, 152, 154, 156, 158, and 160, respectively. For example, in the illustrated embodiment, switch elements 130 and 132 are formed having a generally Z-shaped configuration (e.g., when viewed from a position orthogonal to a plane of movement of switch elements 130 and 132); however, it should be understood that elements 130 and 132 may be otherwise configured.

As best depicted in FIG. 12, circuitry 82 is initially in an open circuit state when mass member 30 is in the non-activated or initial pre-detection state/position 50 (i.e., prior to being subjected to an acceleration event). For example, in this embodiment, in the non-activated or initial pre-detection state/position 50 of mass member 30, segments 154 and 160 are each spaced apart from and/or in disengagement with respective contacts 142 and 144. Thus, if RFID module 84 is activated or energized by RFID reader 100 while mass member 30 is in the non-activated or initial pre-detection state 50 (i.e., prior to being subjected to an acceleration event), RFID module 84 would detect the open circuit condition of circuitry 82 and output or transmit value 92. Responsive to indicator 10 being subjected to an impact or acceleration event of a magnitude sufficient to cause movement of mass member 30 from the initial non-activated position 50 to an activated position (e.g., position 96 or 116), the state of circuitry 82 would change from being in an open circuit condition to a closed circuit condition because the movement of mass member 30 would result in mass member 30 contacting a respective switch element 130 or 132 and cause the respective switch element 130 or 132 to come in contact with and/or engage respective contact 142 or 144, thereby closing a respective circuit. Thus, responsive to movement of mass member 30 from the initial non-activated position 50 to an activated position 96 or 116, if RFID module 84 is activated or energized by RFID reader 100, RFID module 84 would detect the closed circuit condition of circuitry 82 and output or transmit value 94 instead of value 92. Thus, a change in the switch circuitry 82 state causes a change in a value output by RFID module 84 when activated.

In the embodiment illustrated in FIGS. 12-14, each switch element 130 and 132 may be part of and/or otherwise form a different, separate circuit (circuit 162 and 164, respectively) such that RFID module 84 can detect whether either circuit 162 or 164 is in an open or closed circuit condition. For example, if indicator 10 has been subjected to an impact event causing mass member 30 to move from position 50 to position 96, circuit 164 would remain in an open circuit condition, while circuit 162 would have gone from an open circuit condition to a closed circuit condition. RFID module 84 may be configured to function similar to a digital logic OR gate such that a closed value 94 is output if one or both circuits 162 and 164 are in a closed circuit condition. In the embodiment illustrated in FIGS. 12-14, switch circuitry 82 is in an open circuit condition when mass member 30 is in the non-activated or initial pre-detection state/position 50 (i.e., prior to being subjected to an acceleration event). However, it should be understood that indicator 10 may be otherwise configured (e.g., where circuits 162 and 164 would initially be in a closed circuit condition (e.g., switch elements 130 and 132 each in engagement with respective contacts 142 and 144 where movement of mass member into position 96 or 116 causes mass member 30 to disengage a respective switch element 130 or 132 from respective contacts 142 or 144.

FIGS. 15A and 15B are diagrams illustrating a portion of indicator 10 depicted in FIGS. 12-14. In FIGS. 15A and 15B, only switch element 132 is depicted; however, it should be understood that the operation and/or function of switch element 130 is similar to that hereinafter described in connection with switch element 132. In FIG. 15A, indicator 10 has been subjected to an impact event such that mass member 30 has moved in the direction 170 into position 116 such that the movement of mass member 30 towards position 116 has caused mass member 30 to contact switch element 132, thereby causing switch element segment 160 to engage contact 144 to place circuit 164 from an open circuit condition into a closed circuit condition. In FIG. 15B, in response to indicator 10 being subjected to another impact event causing mass member 30 to move in direction 172 away from position 116, although mass member 30 has disengaged from switch element 132 (i.e., mass member 30 is no longer contacting or applying a force to switch element 132), switch element 132 remains in engagement with contact 144 such that circuit 164 remains in a closed circuit condition. In this embodiment, switch element 132 comprises a flexible and/or deformable switch element 132 such that a force applied to switch element 132 by mass member 30 causes switch element 132 to compress within the space directly between contacts 144 and 146, thereby resulting in switch element 132 being maintained in a compressed state between contacts 144 and 146. Being in a compressed state, switch element 132 continues to apply a force to contact 144, thereby maintaining circuit 164 in a closed circuit state after mass member 30 has moved away from position 116 (or away from contacting switch element 132). Thus, embodiments of the present invention provide an irreversible indication of impact activation by maintaining circuit 164 in a closed circuit state once circuit 164 has gone from an open circuit state to a closed circuit state. In the above description, circuit 164 is initially in an open circuit condition and then becomes a closed circuit in response to movement of mass member 30 against switch element 132. However, it should be understood that the open/closed circuit condition or operation could be reversed (e.g., initially in a closed circuit condition where switch element 132 is in engagement with contact 144 where movement of mass member 30 against switch element 132 causes switch element 132 to disengage from contact 144). In this alternate embodiment, another contact or the configuration of switch element 132 may cause circuit 164 to remain in an open circuit state even after mass member 30 moves away from position 116.

FIG. 16 is a diagram illustrating another embodiment of impact indicator 10 in accordance with the present disclosure, FIG. 17 is a diagram illustrating a bottom view of impact indicator 10 of FIG. 16 in accordance with an embodiment of the present disclosure viewed from the line 17-17 in FIG. 16, and FIG. 18 is a diagram illustrating a section view of impact indicator 10 depicted in FIG. 16 in accordance with an embodiment of the present disclosure taken along the line 18-18 of FIG. 16. In FIGS. 16-18, most elements of indicator 10 (e.g., those depicted and described in connection with FIGS. 1-7) have been omitted for clarity and ease of description; however, it should be understood that indicator 10 may be similarly configured as depicted and described in connection with FIGS. 1-7. In the embodiment illustrated in FIGS. 16-18, another embodiment of switching mechanism 80, circuitry 82, and RFID module 84 coupled to switch circuitry 82 are depicted. In the illustrated embodiment, switching mechanism 80 is formed by mass member 30 (e.g., without conductive element 120 (FIGS. 9-11)). For ease of description and clarity, mass member 30 is not depicted in FIGS. 17 and 18. Switch circuitry 82 includes conductive switch elements 170 and 172, and conductive contacts 180, 182, 184, and 186. Switch elements 170 and 172 are located generally in or near respective positions 96 and 116 such that as mass member 30 moves into position 96 or 116 from position 50, mass member 30 contacts or otherwise engages respective switch element 170 or 172. In the illustrated embodiment, switch element 170 is fixedly coupled to contact 180, and switch element 172 is fixedly coupled to contact 186. Switch elements 170 and 172, and contacts 180, 182, 184, and 186, may comprise conductive wires, pins, posts, pads, traces, etc.

In the embodiment illustrated in FIGS. 16-18, switch elements 170 and 172 are arcuately shaped (e.g., when viewed from a position orthogonal to a plane of movement of switch elements 170 and 172) having a convex portion thereof disposed toward mass member 30. In some embodiments, switch elements 170 and 172 comprise flexible switch elements 170 and 172 such that switch elements 170 and 172 may bend/rotate relative to and/or with respective contacts 180 and 186. In the illustrated embodiment (as best illustrated in FIG. 18 relative to contact 182), contacts 182 and 184 are disposed at an angle and/or incline toward mass member 30 (e.g., toward respective switch elements 170 and 172) such that contacts 182 and 184 are disposed at an acute angle relative to a plane of movement of mass member 30 (and respective switch elements 170 and 172). Although FIG. 18 only depicts contacts 182 and 186 (due to the location of the section view), it should be understood that contacts 184 and 180 are similarly configured (e.g., contact 184 disposed at an acute angle toward mass member 30/switch element 172).

As best illustrated in FIG. 17, switch element 172 extends toward contact 184 and bends downwardly near a distal end thereof (e.g., toward a plane parallel to a plane of movement of mass member 30/switch element 172 but closer to a base attachment location of contact 184). For example, in the illustrated embodiment, switch element 172 includes contiguous switch element segments 190, 192, and 194. Segment 190 is fixedly coupled to contact 186 at a proximal end thereof and extends in a direction generally toward contact 184. As segment 190 approaches a location of contact 184 (e.g., prior to reaching contact 184), segment 190 transitions to segment 192 (e.g., an approximate right angle) where segment 192 extends in a direction toward module 84 (i.e., in a direction toward a base of contact 184). Segment 192, prior to reaching module 84, transitions to segment 194 which extends in a direction similar to segment 190 (e.g., an approximate right angle to segment 192). It should be understood that switch element 170 is similarly configured (e.g., bending downwardly near a distal end thereof).

In operation, as best depicted in FIG. 16, circuitry 82 is initially in an open circuit state when mass member 30 is in the non-activated or initial pre-detection state/position 50 (i.e., prior to being subjected to an acceleration event). For example, in this embodiment, in the non-activated or initial pre-detection state/position 50 of mass member 30, switch elements 170 and 172 are each spaced apart from and/or in disengagement with respective contacts 182 and 184. Thus, if RFID module 84 is activated or energized by RFID reader 100 while mass member 30 is in the non-activated or initial pre-detection state 50 (i.e., prior to being subjected to an acceleration event), RFID module 84 would detect the open circuit condition of circuitry 82 and output or transmit value 92. Responsive to indicator 10 being subjected to an impact or acceleration event of a magnitude sufficient to cause movement of mass member 30 from the initial non-activated position 50 to an activated position (e.g., position 96 or 116), the state of circuitry 82 would change from being in an open circuit condition to a closed circuit condition because the movement of mass member 30 would result in mass member 30 contacting a respective switch element 170 or 172 and cause the respective switch element 170 or 172 to come in contact with and/or engage respective contact 182 or 184, thereby closing a respective circuit. Thus, responsive to movement of mass member 30 from the initial non-activated position 50 to an activated position 96 or 116, if RFID module 84 is activated or energized by RFID reader 100, RFID module 84 would detect the closed circuit condition of circuitry 82 and output or transmit value 94 instead of value 92. Thus, a change in the switch circuitry 82 state causes a change in a value output by RFID module 84 when activated.

In the embodiment illustrated in FIGS. 16-18, distal ends of switch elements 170 and 172 and angled downwardly toward a base of respective contacts 182 and 184, and contacts 182 and 184 are disposed at an acute angle toward respective switch elements 170 and 172, to reduce a likelihood of switch elements 170 and 172 from riding up and over a respective contact 182 and 184 (e.g., response to movement of mass member 30). As described above in connection with FIGS. 12-14, each switch element 170 and 172 may be part of and/or otherwise form a different, separate circuit (e.g., circuit 162 and 164, respectively) such that RFID module 84 can detect whether either circuit 162 or 164 is in an open or closed circuit condition. For example, if indicator 10 has been subjected to an impact event causing mass member 30 to move from position 50 to position 96, circuit 164 would remain in an open circuit condition, while circuit 162 would have gone from an open circuit condition to a closed circuit condition. RFID module 84 may be configured to function similar to a digital logic OR gate such that a closed value 94 is output if one or both circuits 162 and 164 are in a closed circuit condition. Further, embodiments of indicator 10 provide an irreversible indication of activation. For example, as described further in connection with FIGS. 1-7, once indicator 10 has been subject to an impact condition of a sufficient magnitude to move mass member away from position 50, spring members 40 and 42 maintain mass member 30 in either position 96 or 116, thereby maintaining switch elements 170 and/or 172 in engagement with respective contacts 182 and 184.

FIG. 19 is a diagram illustrating another embodiment of impact indicator 10 in accordance with the present disclosure. In the embodiment illustrated in FIG. 19, indicator 10 is configured similarly to as depicted and described in connection with FIGS. 16-18 except instead of a single switch element 170 and 172, a plurality of distinct switch elements 170 and 172 are coupled to respective contacts 180 and 186. For example, in the illustrated embodiment, three switch elements 170 (e.g., switch elements 170 ₁, 170 ₂, and 170 ₃) are coupled to contact 180, and three switch elements 172 (e.g., switch elements 172 ₁, 172 ₂, and 172 ₃) are coupled to contact 186. It should be understood that a greater or fewer quantity of switch elements 170 and 172 may be used. In the illustrated embodiment, multiple switch elements 170 and 172 are used to increase the likelihood of initiating a circuit state change (e.g., triggering a closed circuit condition from an open circuit condition, or vice versa). For example, using multiple switch elements 170 and 172 increases the likelihood of a circuit state change should one or more switch elements 170 and 172 fail or fail to engage respective contacts 182 and 184.

FIG. 20 is a diagram illustrating another embodiment of impact indicator 10 in accordance with the present disclosure. In FIG. 20, most elements of indicator 10 (e.g., those depicted and described in connection with FIGS. 1-7) have been omitted for clarity and ease of description; however, it should be understood that indicator 10 may be similarly configured as depicted and described in connection with FIGS. 1-7. In the embodiment illustrated in FIG. 20, another embodiment of switching mechanism 80, circuitry 82, and RFID module 84 coupled to switch circuitry 82 are depicted. In the illustrated embodiment, switching mechanism 80 is formed by mass member 30 (e.g., without conductive element 120 (FIGS. 9-11)). Impact indicator 10 of FIG. 20 is configured similar to as that depicted and described in connection with FIGS. 12-14 except switch circuitry 82 includes conductive switch elements 200 and 202. Switch elements 200 and 202 are located generally in or near respective positions 96 and 116 such that as mass member 30 moves into position 96 or 116 from position 50, mass member 30 contacts or otherwise engages respective switch element 200 or 202. In the illustrated embodiment, switch element 200 is fixedly coupled to contact 140, and switch element 202 is fixedly coupled to contact 146.

In the embodiment illustrated in FIG. 20, switch element 200 includes contiguous switch element segments 210, 212, 214, and 216 where segment 210 is fixedly coupled to contact 140. Switch element 200 comprises a flexible switch element 200 such that one or more of segments 210, 212, 214, and 216 are movable in angular relationship relative to each other, and segment 210 may bend/rotate relative to and/or with contact 140. Similarly, switch element 202 includes contiguous switch element segments 220, 222, 224, and 226 where segment 220 is fixedly coupled to contact 146. Switch element 202 also comprises a flexible switch element 202 such that one or more of segments 220, 222, 224, and 226 are movable in angular relationship relative to each other, and segment 220 may bend/rotate relative to and/or with contact 146. In the illustrated embodiment, switch elements 200 and 202 include non-linear switch element segments 210, 212, 214, 216, 220, 222, 224, and 226, respectively. For example, in the illustrated embodiment, switch elements 200 and 202 are formed having a generally modified Z-shaped configuration (e.g., when viewed from a position orthogonal to a plane of movement of switch elements 200 and 202); however, it should be understood that elements 200 and 202 may be otherwise configured.

In the illustrated embodiment, segment 210 extends from contact 140 toward mass member 30 and transitions to segment 212 such that segment 212 is in a direction substantially perpendicular to a direction of movement of mass member 30 (i.e., in an initial state/position). Segment 212 transitions to segment 214 such that segments 214 and 216 form an acute angle relative to each other (e.g., an open-sided acute triangle) in a spring-like configuration such that segment 216 extends in a direction toward mass member 30 at an acute angle relative to segment 214 (e.g., with the open-side of the acute triangle facing mass member 30). Segments 214 and 216 form a compressible spring at a distal end of switch element 200. In the embodiment illustrated in FIG. 20, switch element 202 (and segments 220, 222, 224, and 226) are configured similarly to as that described in connection with switch element 200.

In the illustrated embodiment, switch elements 200 and 202 have a Z-shaped configuration with a profile or maximum width less than that depicted in FIGS. 12-14 (e.g., relative to switch elements 130 and 132). In FIG. 20, circuitry 82 is initially in an open circuit state when mass member 30 is in the non-activated or initial pre-detection state/position 50 (i.e., prior to being subjected to an acceleration event). For example, in this embodiment, in the non-activated or initial pre-detection state/position 50 of mass member 30, segments 216 and 226 are each spaced apart from and/or in disengagement with respective contacts 142 and 144. Thus, if RFID module 84 is activated or energized by RFID reader 100 while mass member 30 is in the non-activated or initial pre-detection state 50 (i.e., prior to being subjected to an acceleration event), RFID module 84 would detect the open circuit condition of circuitry 82 and output or transmit value 92. Responsive to indicator 10 being subjected to an impact or acceleration event of a magnitude sufficient to cause movement of mass member 30 from the initial non-activated position 50 to an activated position (e.g., position 96 or 116), the state of circuitry 82 would change from being in an open circuit condition to a closed circuit condition because the movement of mass member 30 would result in mass member 30 contacting a respective switch element 200 or 202 and cause the respective switch element 200 or 202 to come in contact with and/or engage respective contact 142 or 144, thereby closing a respective circuit. Thus, responsive to movement of mass member 30 from the initial non-activated position 50 to an activated position 96 or 116, if RFID module 84 is activated or energized by RFID reader 100, RFID module 84 would detect the closed circuit condition of circuitry 82 and output or transmit value 94 instead of value 92. Thus, a change in the switch circuitry 82 state causes a change in a value output by RFID module 84 when activated.

As described above in connection with FIGS. 12-14, each switch element 200 and 202 may be part of and/or otherwise form a different, separate circuit (circuit 162 and 164, respectively) such that RFID module 84 can detect whether either circuit 162 or 164 is in an open or closed circuit condition. Similar to as described and depicted in connection with FIGS. 15A and 15B, although mass member 30 may disengaged from switch element 200 or 202 (i.e., mass member 30 is no longer contacting or applying a force to switch element 200 or 202), switch element 200 and/or 202 remains in engagement with respective contacts 142 and 144 such that circuit 162 and/or 164 remains in a closed circuit condition. In this embodiment, switch elements 200 and 202 comprise a flexible and/or deformable switch element 200 and 202 such that a force applied to switch element 200 and/or 202 by mass member 30 causes switch element 200 and/or 202 to compress within the space directly between contacts 144 and 146 (e.g., at least respective segments 214/216 and 224/226, thereby resulting in segments 214/216 and 224/226 being maintained in a compressed state against respective contacts 142 and 144. Being in a compressed state, switch elements 200 and 202 continues to apply a force to respective contacts 142 and 144, thereby maintaining circuit 162 or 164 in a closed circuit state after mass member 30 has moved away from position 96 or 116 (or away from contacting switch element 200 or 202). Thus, embodiments of the present invention provide an irreversible indication of impact activation by maintaining circuit 162 or 164 in a closed circuit state once circuit 162 or 164 has gone from an open circuit state to a closed circuit state. In the above description, circuits 162 and 164 are initially in an open circuit condition and then become a closed circuit in response to movement of mass member 30 against switch elements 200 or 202. However, it should be understood that the open/closed circuit condition or operation could be reversed (e.g., initially in a closed circuit condition where switch element 200 is in engagement with contact 142 where movement of mass member 30 against switch element 200 causes switch element 200 to disengage from contact 142). In this alternate embodiment, another contact or the configuration of switch element 200 may cause circuit 162 to remain in an open circuit state even after mass member 30 moves away from position 96.

FIG. 21 is a diagram illustrating a portion of impact indicator 10 depicted in FIG. 20 according to an embodiment of the present disclosure. In FIG. 21, only switch element 202 is depicted; however, it should be understood that the operation and/or function of switch element 200 is similar to that hereinafter described in connection with switch element 202. In FIG. 21, indicator 10 has been subjected to a first impact event such that mass member 30 has initially moved into position 116 such that the movement of mass member 30 towards position 116 has caused mass member 30 to contact switch element 202, thereby causing switch element segment 226 to engage contact 144 to place circuit 164 from an open circuit condition into a closed circuit condition. In FIG. 21, in response to indicator 10 being subjected to another impact event causing mass member 30 to move in direction 172 away from position 116, although mass member 30 has disengaged from switch element 202 (i.e., mass member 30 is no longer contacting or applying a force to switch element 202), switch element 202 remains in engagement with contact 144 such that circuit 164 remains in a closed circuit condition. In this embodiment, switch element 202 comprises a flexible and/or deformable switch element 202 such that a force applied to switch element 202 by mass member 30 causes switch element 202 to compress and/or deflect within the space directly between contacts 144 and 146, thereby resulting in switch element 202 being maintained in a compressed state between contacts 144 and 146. Being in a compressed state, switch element 202 continues to apply a force to contact 144, thereby maintaining circuit 164 in a closed circuit state after mass member 30 has moved away from position 116 (or away from contacting switch element 202). For example, segments 224 and 226 form a compressed leaf spring biased against contact 144 to maintain switch element 202 in engagement with contact 144. Thus, embodiments of the present invention provide an irreversible indication of impact activation by maintaining circuit 164 in a closed circuit state once circuit 164 has gone from an open circuit state to a closed circuit state. In the above description, circuit 164 is initially in an open circuit condition and then becomes a closed circuit in response to movement of mass member 30 against switch element 202. However, it should be understood that the open/closed circuit condition or operation could be reversed (e.g., initially in a closed circuit condition where switch element 202 is in engagement with contact 144 where movement of mass member 30 against switch element 202 causes switch element 202 to disengage from contact 144). In this alternate embodiment, another contact or the configuration of switch element 202 may cause circuit 164 to remain in an open circuit state even after mass member 30 moves away from position 116.

FIG. 22 is a block diagram representing and illustrating an embodiment of an unmanned aerial vehicle (UAV) impact indicator monitoring system 300 in accordance with an embodiment of the present disclosure. In FIG. 22, system 300 includes a UAV 302 and an item or package 304 that may be flown by UAV 302 to a particular destination (e.g., from an origin (such as a vendor location) to a destination (such as a consumer), or vice versa). In the illustrated embodiment, package 304 includes an impact indicator 306 attached, affixed, and/or otherwise secured thereto. It should be understood that, as used herein, “package” 304 may include a particular object or item, or a package/container containing an object or item. Impact indicator 306 is configured to detect and indicate whether package 304 has been subjected to a sufficient magnitude of an impact or acceleration event, thereby causing an activation status of impact indicator 306 to change from a non-activated state to an activated state. For example, impact indicator 306 may comprise indicator 10 as depicted and described in FIGS. 1-21. However, it should be understood that impact indicator 306 may comprise other types of impact indicators (e.g., an impact indicator as depicted and described in U.S. Pat. No. 8,863,683 which is incorporated herein by reference in its entirety; an impact indicator as depicted and described in U.S. Pat. No. 9,103,734 which is incorporated herein by reference in its entirety; an impact indicator as depicted and described in U.S. Pat. No. 9,103,849 which is incorporated herein by reference in its entirety; an impact indicator as depicted and described in U.S. Pat. No. 9,116,058 which is incorporated herein by reference in its entirety; and other types of impact indicators, including shock/impact indicators that are commercially available under the name ShockWatch® from ShockWatch, Inc., of Dallas, Tex.)

In the embodiment illustrated in FIG. 22, UAV 302 includes a propulsion/guidance system 310 configured to fly UAV 302, a power source 312 (e.g., a battery) to provide power to various mechanisms of UAV 302, an antenna 314, a transceiver 316 for transmitting and receiving communications (e.g., wireless communications via antenna 314), an altimeter 318, a retention mechanism 320 configured to pick up, retain, and release an object (e.g., package 304) by UAV 302, and a GPS receiver 321. In the illustrated embodiment, UAV 304 also includes a memory 322 having a controller 324, a GPS module 326, a communications module 328, and UAV data 330. Propulsion/guidance system 310 may include one or more propellers, ailerons, rudders, etc., for enabling the flight and movement of UAV 302. Altimeter 318 may be any device which can provide the altitude of UAV 302 (e.g., the height above a delivery destination). Retention mechanism 320 may comprise, but not be limited to, one or more of a claw, gripper, or grapple, a releasable clamp, a bomb bay, a hook and eyelet, controllable jaws and eyelets, devices which may partially penetrate package 304 (e.g., tongs), a suction device, a line or tether (e.g., being retractable relative to UAV 302 for lowering/raising package 304 relative thereto), etc.

In some embodiments, controller 324 is configured to control the operation of UAV 302 for retrieving/delivering package 304. For example, in some embodiments, GPS module 326 may be used to gather/process geopositional data of UAV 302 (e.g., using geopositional data acquired via GPS receiver 321). Controller 324 may also receive the GPS coordinates of an origin and/or delivery destination of package 304 (e.g., wirelessly or though a physical connection/port). The GPS coordinates of an origin and/or delivery destination of package 304 may be stored in memory 322 as UAV data 330 (e.g., delivery data 332). Controller 324 may activate propulsion/guidance system 310 to take off and fly toward a desired location, and GPS module 326 may acquire GPS data regarding UAV 302 and interface with controller 324 for controlling the direction and movement of UAV 302 to a desired location. Altimeter 318 provides altitude information also used by controller 324 for controlling the movement and altitude of UAV 302. Communications module 328 may be used for transmitting/receiving various types of information relative to UAV 302 (e.g., via a network 340 to a server 342 or other remote location). For example, network 340 may comprise any type of wired and/or wireless network (e.g., a local area network (LAN), a wide area network (WAN), a Wi-Fi or cellular network, etc.). It should also be understood that communications module 328 may be configured for a variety of types of wireless communications, modes, protocols, and/or formats (e.g., short-message services (SMS), wireless data using General Packet Radio Service (GPRS)/3G/4G or through public internet via Wi-Fi, or locally with other radio-communication protocol standards such as Wi-Fi, Z-Wave, ZigBee, Bluetooth®, Bluetooth® low energy (BLE), LoRA, NB-IoT, SigFox, Digital Enhanced Cordless Telecommunications (DECT), or other prevalent technologies). Further details of UAV 302, including operational characteristics and/or methods for grasping/transporting/releasing package 304 is described in U.S. Pat. No. 9,536,216, which is incorporated herein by reference in its entirety. It should be understood that UAV 302 may be otherwise configured to facilitate its characteristics for flying and/or grasping/transporting/releasing package 304.

In the embodiment illustrated in FIG. 22, UAV 302 also includes an indicator reader device 350. Indicator reader device 350 may include any type of device for viewing and/or reading an indication of impact activation of impact indicator 306 on package 304. For example, indicator reader device 350 may comprise, but not be limited to, a camera 352, an RFID reader 354 (e.g., such as RFID reader 100 as described above), and/or a barcode reader 356. In the illustrated embodiment, UAV 302 also includes an indicator reader module 360 and indicator data 362 (e.g., depicted as being stored in memory 322). Indicator reader module 360 is configured to receive information corresponding to indicator 306 (e.g., captured and/or otherwise acquired by reader device 350) and determine an activation status of impact indicator 306. Indicator data 362 may comprise information associated with a prior and/or current activation status of indicator 306, or may comprise information enabling module 360 to assess the information acquired by reader device 350 to determine the activation status of indicator 306. For example, indicator reader module 360 may be configured to derive an activation status of indicator 306 based on an image captured by camera 352 (e.g., by detecting a color, a color change, or other type of visual indication), based on a value emitted by indicator 306 (e.g., a value emitted by a passive RFID tag as described above), a value represented and/or otherwise defined by a barcode or other type of code, etc. In some embodiments, indicator reader module 360 may be configured to access indicator data 362 to compare currently acquired information with previously acquired information (e.g., comparing two different image captures of indicator 306 acquired at two different times), compare acquired information with stored information (e.g., access a relational database to determine whether a current value indicated by indicator 306 indicates an activation status), or otherwise assess an activation state of indicator 306. In some embodiments, the activation status of indicator 306 may be communicated to a remote location (e.g., to server 342 via communications module 328).

Thus, the present invention may include computer program instructions at any possible technical detail level of integration (e.g., stored in a computer readable storage medium (or media) (e.g., memory 322) for causing a processor to carry out aspects of the present invention. Computer readable program instructions described herein can be downloaded to respective computing/processing devices (e.g., communications module 328 and/or indicator reader module 360). Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages. In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention. Aspects of the present invention are described herein with reference to illustrations and/or block diagrams of methods and/or apparatus according to embodiments of the invention. It will be understood that each block of the illustrations and/or block diagrams, and combinations of blocks in the illustrations and/or block diagrams, may represent a module, segment, or portion of code, can be implemented by computer readable program instructions. These computer readable program instructions may be provided to a processor or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the illustrations and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computing device, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the illustrations and/or block diagram block or blocks.

Controller 324, GPS module 326, communications module 328, and/or indicator reader module 360 may be implemented in any suitable manner using known techniques that may be hardware-based, software-based, or some combination of both. For example, controller 324, GPS module 326, communications module 328, and/or indicator reader module 360 may comprise software, logic and/or executable code for performing various functions as described herein (e.g., residing as software and/or an algorithm running on a processor unit, hardware logic residing in a processor or other type of logic chip, centralized in a single integrated circuit or distributed among different chips in a data processing system). As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, method or computer program product. Accordingly, aspects of the present disclosure may take the form of a hardware embodiment, a software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.”

FIG. 23 is a diagram illustrating an embodiment of UAV impact indicator monitoring system 300 in accordance with an embodiment of the present disclosure. In FIG. 23, UAV 302 has indicator reader device 350 attached or coupled thereto, and package 304 is detachably coupled to UAV 302 by retention mechanism 320. Indicator reader device 350 is located and/or otherwise oriented in a position on UAV 302 to facilitate the acquisition of status information pertaining to indicator 306 (e.g., with a line of sight to indicator 306, in proximity to indicator 306 to read a value displayed or emitted by indicator 306 (e.g., such as an RFID value), etc.). In operation, package 304 is transferred or flown from one location (e.g., an origin) to another location (e.g., a destination). For example, UAV 302 may be used to deliver package 304 to a customer that has placed an order for a particular object or item from a merchant or other entity, retrieve package 304 from a customer that is returning an object or item to a merchant, retrieving package 304 from a warehouse and delivering same to a distribution center, etc. In the illustrated embodiment, package 304 has impact indicator 306 attached thereto. If package 304 has been subject to an impact event over a certain threshold, indicator 306 detects such event and undergoes a change to indicate such an event (e.g., transitioning from a non-activated state to an activated state). As described above, indicator reader device 350 may acquire information associated with indicator 306 (e.g., capture an image, detect an RFID value, read a barcode, etc.) and indicator reader module 360 may assess such information to derive an activation status of indicator 306.

In some embodiments, indicator reader module 360 is configured to cause reader device 350 to acquire information pertaining to indicator 306 at various times. For example, in some embodiments, module 360 is programmed to cause device 350 to acquire information as to indicator 306 prior to grasping or retaining package 304 by UAV 302, after grasping/retaining package but prior to package 304 being released from UAV 302, and/or after package 304 has been released by UAV 302. If module 360 determines that package 304 has been subject to an impact event over a certain threshold (as indicated by a current status of indicator 306), UAV 302 may be programmed to perform, or not perform, a particular action (e.g., not grasp package 304, not release/deliver package 304, return package 304 to its origin, etc.). As an example, should the delivery method involve dropping package 304 from what is considered some safe height (or even releasing retention mechanism 320 upon package 304 being in contact with the ground or other surface), module 360 may be configured to cause reader device 350 to read indicator 306 (e.g., capture an image and/or otherwise read a value associated with indicator 306) after package 304 has been released from retention mechanism 320. In response to module 360 determining that indicator 306 indicates an activated status, module 360 may be configured to cause retention mechanism 320 to reacquire package 304 (e.g., interfacing with controller 324 to cause retention mechanism 320 to re-grasp package 304 to enable package 304 to be returned to its origin). Similarly, if module 360 detects an activated status of indicator 306 prior to grasping package 304 for delivery of package 304, or if module 360 detects an activated status of indicator 306 prior to releasing retention mechanism 320, module 360 may cause UAV 302 (e.g., interfacing with controller 324) to not grasp package 304 or not release/deliver package 304, respectively). If module 360 detects that indicator 306 has remained in a non-activated status, module 360 may interface with controller 324, if necessary, to enable UAV 302 to continue its program or operation(s).

In some embodiments, indicator data 362 may comprise information associated with when, or at what intervals, to acquire information pertaining to the activation status of indicator 306. For example, in some embodiments, reader module 360 may access indicator data 362 to determine when to cause reader device 350 to acquire information as to indicator 306 (e.g., prior to activating retention mechanism 320 (to either grasp or release), after activating retention mechanism 320 (after grasping or releasing), at periodic intervals, etc.). In some embodiments, reader module 360 may store a current activation status of indicator 306 as determined by module 360 (e.g., along with a time or clock value), may store captured images of indicator 306, and/or interface with communications module 328 to cause the communication of a current status of indicator 306 (along with any acquired data 362 pertaining to the activation status of indicator 306) to a remote location (e.g., server 342).

Thus, regardless of how UAV 302 might deliver or transport package 304, there may there may be potential damage to package 304 (as a result of the transportation/delivery of package 304 or prior thereto). For example, package 304 may be inadvertently dropped, UAV 302 may mistakenly fly into a tree, etc. System 300 enables a condition of package 304 to be monitored in connections with its transportation from an origin to a destination. It should be understood that various features of system 300 may also be remotely activated. For example, in some embodiments, a user may remotely control and/or interface with UAV 302 and cause reader device 350 to acquire information pertaining to indicator 306. For example, in some embodiments, UAV 302 may receive a signal to cause camera 352 to acquire an image of indicator 306, cause RFID reader 354 to energize a passive RFID tag of indicator 306 to acquire a value therefrom, cause barcode reader 356 to read a barcode displayed by indicator 306, etc. Module 360 may assess the acquired information and determine/communicate an activation status of indicator 306. It should also be understood that, in some embodiments, reader module 360 (or portions/certain functions thereof) may be omitted from UAV 302 and, instead, be remotely located (e.g., residing on server 342 or elsewhere). In such an embodiment, for example, information acquired by indicator reader device 350 may be communicated from UAV 302 to a remote location (e.g., server 342) where a determination of impact indicator 306 activation status is then made. Based on the determined activation status of impact indicator 306, various operational control parameters may be communicated to UAV 302.

FIG. 24 is a flow diagram illustrating an embodiment of a method for UAV impact indicator monitoring. The method begins at block 400, where an operation or procedure to pick-up or grasp package 304 is initiated. At block 402, module 360 causes reader device 350 to acquire information/data pertaining to impact indicator 306 (e.g., capturing a photographic image, reading a barcode, reading an RFID value, etc.). At decisional block 404, module 360 determines whether the acquired information indicates an activated status of indicator 306. If so, the method proceeds to block 406, where the pick-up operation of package 304 is aborted. If at decisional block 404 it is determined that indicator 306 is in a non-activated state, the method proceeds from decisional block 404 to block 408, where retention mechanism 320 is actuated/activated to grasp or otherwise pick-up package 304. At block 410, UAV 302 is operated to transport package 304 to a destination.

At block 412, an operation or procedure to drop-off/release/deliver package 304 is initiated. At block 414, module 360 causes reader device 350 to acquire information/data pertaining to impact indicator 306 (e.g., capturing a photographic image, reading a barcode, reading an RFID value, etc.). At decisional block 416, module 360 determines whether the acquired information indicates an activated status of indicator 306. If so, the method proceeds to block 418, where the delivery or drop-off operation of package 304 is aborted, and then the method proceeds to block 420 where UAV 302 is controlled/operated to return to its origin. If at decisional block 416 it is determined that indicator 306 is in a non-activated state, the method proceeds from decisional block 416 to block 422, where retention mechanism 320 is actuated/activated to release package 304.

At block 424, module 360 causes reader device 350 to acquire information/data pertaining to impact indicator 306 (e.g., capturing a photographic image, reading a barcode, reading an RFID value, etc.). At decisional block 426, module 360 determines whether the acquired information indicates an activated status of indicator 306. If so, the method proceeds to block 428, where retention mechanism 320 is actuated/activated to re-acquire package 304 (e.g., grasping or otherwise picking up package 304), and then the method proceeds to block 430 where UAV 302 is controlled/operated to return to its origin. If at decisional block 426 it is determined by module 360 that indicator 306 is in a non-activated state, the method proceeds from decisional block 426 to block 430 where UAV 302 is controlled/operated to return to its origin.

Thus, embodiments of the present disclosure enable impact and/or acceleration event detection for package delivery using a UAV. Embodiments of the present disclosure enable the UAV to collect information as to the activation status of an impact indicator associated with a package being delivered or to be delivered such that the condition of the package may be ascertained throughout the delivery operation (e.g., beginning prior to package acquisition and extending until a delivery operation has been successfully completed without incurring a potentially detrimental impact event.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated. 

What is claimed is:
 1. An unmanned aerial vehicle (UAV), comprising: a propulsion system configured to fly the UAV carrying a package containing an impact indicator to a destination; a retention mechanism for retaining and releasing the package carried by the UAV; a camera for capturing an image of the impact indicator; and circuitry configured to determine a status of the impact indicator.
 2. The UAV of claim 1, further comprising communications circuitry configured to transmit the status to a server.
 3. The UAV of claim 1, wherein the circuitry is configured to derive the status from the captured image.
 4. The UAV of claim 1, further comprising an indicator reader device configured to read a value from the impact indicator, the value indicating the status of the impact indicator.
 5. The UAV of claim 4, wherein the indicator reader device includes a radio-frequency identification (RFID) reader.
 6. The impact indicator of claim 4, wherein the indicator reader device includes a barcode reader.
 7. An unmanned aerial vehicle (UAV), comprising: a propulsion system configured to fly the UAV to a destination; a retention mechanism for retaining and releasing a package carried by the UAV; and circuitry configured to: prior to the retention mechanism releasing the package at the destination, determine a status of an impact indicator attached to the package; and responsive to determining that the status indicates an activation of the impact indicator, abort a release of the package by the retention mechanism at the destination.
 8. The impact indicator of claim 7, wherein the circuitry is configured to, after releasing the package at the destination, determine the status of the impact indicator.
 9. The impact indicator of claim 7, further comprising a radio-frequency identification (RFID) reader configured to read a value emitted by the impact indicator.
 10. The impact indicator of claim 7, further comprising a camera configured to capture an image of the impact indicator, the circuitry configured to determine the status of the impact indicator from the captured image.
 11. The impact indicator of claim 7, further comprising a barcode reader configured to read a barcode of the impact indicator, the circuitry configured to determine the status of the impact indicator from the barcode.
 12. An unmanned aerial vehicle (UAV), comprising: a propulsion system configured to fly the UAV carrying a package containing an impact indicator to a destination; a retention mechanism for retaining and releasing the package carried by the UAV; an indicator reader device configured to read a value from the impact indicator, the value indicating the status of the impact indicator; and circuitry configured to determine a status of the impact indicator; wherein the indicator reader device includes a barcode reader.
 13. The UAV of claim 12, wherein the indicator reader device includes a radio-frequency identification (RFID) reader. 